Systems and methods for intelligent layered interactive programmatic elements for fixed content

ABSTRACT

The disclosed systems and methods relate to the creation and use of fixed-layout display component(s) embedded as part of the overall programmatic device(s) screen display(s). In preferred embodiments, these fixed-layout components may behave in a specific manner and can be utilized and managed independently of the remaining programmatically generated screen display functionality. A fixed-layout component may contain many elements and associated user interactivities. Each element may be related positionally, dimensionally and display sequence to the overall component and to other elements contained such that the mathematical calculation of relative position, size and dimension aspect ratio of all the component items and the item display sequence is maintained programmatically and visually relative to each other irrespective of the device screen size or orientation when the fixed-layout component is part of an overall display. Advantages include rapid embedding of fixed-layout component(s) into device(s) display application(s).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of, and priority to, U.S.provisional application Ser. No. 62/447,459 filed on Jan. 18, 2017, theentire specification of which is incorporated herein by reference.

BACKGROUND OF THE INVENTION Field of the Art

The disclosure relates to the field of systems interactivity, and moreparticularly to the field enabling fixed-layout content to receive inputand communication with interactive systems.

Discussion of the State of the Art

Content (text, graphics, photos, images, and/or any combination ofthese) may be developed in a wide variety of content or generalauthoring applications at present. This content can then be printed orexported out to a variety of formats depending on the feature/functionsof the original source content or authoring user application. Thiscontent, which is already authored and available may be required,specifically in business environments, to be re-used in otherapplication software systems or servers comprising database(s), filestorage systems, workflow and other logic operations. Various methodsmay be available to export out this content from these authoringapplications so that it can be re-used in some way for these otherpurposes. The content export approach from these source/authoringapplications may be dependent on the available functions within thesesource application which create, and is often typically via an option(a) comprising all the elements at their lowest level (text, graphics,photos, images, etc.) or via an option (b) comprising an overall graphicimage (i.e. snapshot) which preserves the original content layoutexactly as it would be presented visually to an end user in anassociated original source application, via some combination of Option(a) and (b), or via some other processes. If option (a) is available, itmay require additional manual efforts to extract and then condition andclean the content so that it is re-useable in the mentioned systems,whereby these manual efforts will result in additional time andassociated cost. If option (b) is used, this will result in fixed-layoutcontent image(s) being exported, and if the user then wishes to extractout some or all of the elements (text, graphics, photos, images, etc.),they may need further additional content extraction tools, e.g. opticalcharacter recognition (OCR), combined with a plurality of manual effortsto extract and clean the elements for re-use, which results in incurringsignificantly more time and cost as compared to option (a). Any furthercombinations of options (a) and (b), or other derivative methods, willalso all drive additional time effort and cost to complete. Manual timeeffort and cost problem can become a very large problem if the volume ofcontent is high. It is typical for business enterprises to have tens ofthousands, if not millions, of pages of content where there is apressing requirement to re-use this content in application software andserver systems with databases, file systems, workflow managementsystems, and/or other logic systems as outlined previously, whichamplifies the problem. Typically replacing this content into aninteractive form requires an unreasonable amount of time and cost, andin some cases, there are mandatory requirements to exactly preserve theoriginal content layout precisely (i.e. precise fixed-layout content).Accordingly, many business enterprises choose option (b) describedabove, incurring additional time and huge costs to complete.Fixed-layout content is defined as being a precise and accurate (forexample, pixel by pixel, or using an alternative unit of measure)representing the original source authored content.

All of the above methods are focused on exporting or extracting and orconditioning content for further re-use, and combining this with logicto arrive at new systems and server applications, and to deliver newuser experiences for the end user. Accordingly, content extraction,conditioning, and re-use methods, known in the art, incur time and costto complete. Further, some options outlined above provide lessflexibility for content re-use than others in the creation of newapplication processes and systems and servers.

What is needed are systems and methods to easily extract and combineextracted content with programmatic elements to programmatic systems andservers in a way that: (a) significantly reduces time (including manualadditional processes) and associated cost for extraction andconditioning of content; (b) allows for original source content to becombined easily with programmatic element systems and servers; (c)allows separated control and behavior of the extracted content comparedto programmatic elements; (d) allows for easy association ofprogrammatic elements to extracted content; and, (e) supports sizescaling of extracted content such that all associated programmaticelements automatically and dynamically re-size/re-scale relative toother programmatic elements within the extracted content while actingindependently of programmatic system and servers.

SUMMARY OF THE INVENTION

Accordingly, the inventor has conceived and reduced to practice, invarious embodiment of the invention, systems and methods toprogrammatically generate and managing embedded fixed-layoutcomponent(s), and direct associated items or user interactivities into adisplay component of a computer system user interface, that may behaveindependently of other programmatically generated display components. Apreferred embodiment of the invention relates to the use of takingfixed-layout content as discussed in the background to enable re-usablecontent with significantly greater user functionality and reduced timeand associated cost to prepare. Interaction may be received from a userdevice though various elements and associated interactivities that maybe configured as part of these specific component(s). Anetwork-connected component layout computer comprising a processor, adatabase, a memory, and programming instructions stored in the memory,the programming instructions, when executed by the processor maydynamically generate and manage a plurality of fixed-layout componentsthat may be part of a computer system interface whereby the interfacemay behave in a seamless manner when displayed to a user. That is, auser may not notice a difference between fixed and programmaticcomponents. The plurality of fixed-layout components may be independentand may behave independently of the other programmatic elements ofcomputer systems across a range of devices, display sizes, displayorientations, and/or underlying system operating system.

In some embodiments, one or more fixed-layout components may beintegrated within online or native installed user device applicationsexecuting on a display of a computing system. In some embodiments, theremay be many fixed-layout content components embedded in the overall userinterface display.

The one or more fixed-layout components, and direct associated items maybe linked to each other (within the component) via associated dimensionsand positional data, and may be collectively referred to hereinafter as“component”.

In some embodiments, one or more fixed-layout components and directassociated elements may proportionally re-scale, in size, exactly andrelative to each other, depending on the screen size of a user interfacedisplay of a target computer device; and may be independent of otherre-scaling and re-alignments performed by remaining elements of the userinterface.

An embedding approach for fixed-layout components and direct associateditems may provide an additional method of building a component of acomputer system user interface that may be then seamlessly embedded intoan overall programmatic derived user interface display. Thisfixed-layout component inclusion in a user interface provides analternative and fast method to having to programmatically recreatecontent elements in a manner (for example, from digital print media)that may exactly replicate, including aspect ratio, positional data,original content item, and which may behave independently of theprogrammatic display for a user device or orientation. Direct associatedelements may then be directly linked to this fixed-layout component foradditional user visual presentation and additional interactions receivedfrom user devices. In some embodiments, direct associated elements mayalso support interactions received from a user device with an ability toreceive user-entered data that may then be re-associated with the one ormore fixed-layout components.

In some embodiments, the user interface comprising the fixed-layoutcomponent and the direct associated elements may be displayed on acomputing device for example, via an online application or a nativedevice installed application, and an associated one or more fixed-layoutcomponents and associated elements may present in the same proportion,position, dimension, relative dimension, and independently of properties(size, display, orientation, etc.) of the user device.

Exemplary embodiments of the systems and methods described hereincomprise generation of one or more fixed-layout components, assemblage,and usage of the components while providing reliance on positional anddimensional (and other data types) for at least a portion of the itemscontained within each fixed-layout component.

BRIEF DESCRIPTION OF THE DRAWING FIGURES

The accompanying drawings illustrate several embodiments of theinvention and, together with the description, serve to explain theprinciples of the invention according to the embodiments. It will beappreciated by one skilled in the art that the particular embodimentsillustrated in the drawings are merely exemplary, and are not to beconsidered as limiting of the scope of the invention or the claimsherein in any way.

FIGS. 1A and 1B illustrate an exemplary user device screen detailing theprogrammatic display area and an embedded fixed-layout componentdisplay, according to an embodiment of the invention;

FIGS. 2A and 2B illustrate an exemplary expanded view of a fixed-layoutdisplay component, according to an embodiment of the invention;

FIG. 3 illustrates an exemplary definition of dimensions of a pluralityof fixed-layout component according to an embodiment of the invention;

FIG. 4 illustrates an exemplary definition of dimensions of a pluralityof element items that may be part of a fixed-layout component display,according to an embodiment of the invention;

FIGS. 5A and 5B illustrate an example of positional dimensions of anelement in relation to a defined reference location on an overallfixed-layout component area, according to an embodiment of theinvention;

FIGS. 6B and 6B illustrate examples of different reference positionlocation for a plurality of elements and a reference position locationfor the overall fixed-layout component area, according to an embodimentof the invention;

FIGS. 7A and 7B illustrate an example of interactivity between elementareas and calculation of position and dimensions, according to anembodiment of the invention;

FIG. 8 illustrates an example of the various data stores associated withitems as part of one or more fixed-layout area display components,according to an embodiment of the invention;

FIG. 9 is a high-level flow diagram illustrating an exemplary processfor calculation of all dimension data for items which may be part of afixed-layout component area, according to an embodiment of theinvention;

FIGS. 10A, 10B, and 10C illustrate an example of a fixed area windowwhich may be part of the overall user programmatic display window in adisplay screen, according to an embodiment of the invention;

FIG. 11 illustrates a plurality of exemplary fixed-layout windows and acomponent contained therein as it is repositioned and automaticallyresized in various device screens sizes, according to an embodiment ofthe invention;

FIG. 12 illustrates various examples of a fixed-layout window and afixed-layout component contained inside a display screen as it isrepositioned and resized according to one specific device screens indifferent orientations, according to an embodiment of the invention;

FIG. 13 illustrates an exemplary interaction between a user device and aserver system in the context of an online connected software program,according to an embodiment of the invention;

FIG. 14 illustrates an exemplary interaction between a user devicecomprising a full application program and an online server system,according to an embodiment of the invention;

FIG. 15 is a high-level flow diagram illustrating an exemplary processfor programmatically loading and displaying a plurality of andfixed-layout components, according to an embodiment of the invention;

FIGS. 16A and 16B illustrate an exemplary embodiment of a fixed-layoutcomponent combined with programmatic display elements on a tablet userdevice screen with a plurality of orientations, according to anembodiment of the invention;

FIGS. 17A and 17B illustrate exemplary system components which may beused with the system, according to an embodiment of the invention;

FIG. 18 illustrates an exemplary fixed-layout component which maycomprise a fixed-layout content “background” area, and any number ofdigital graphics (to make up a full or partial area), visual items(text, pictures, etc.), that may comprise a plurality of highlightedareas embedded as part of any number of digital graphics, according toan embodiment of the invention;

FIG. 19 is a high-level flow diagram illustrating at a high level anexemplary process for an automatic finding and calculation of elementitem areas and associated data for data stores, according to anembodiment of the invention;

FIG. 20 is a block diagram illustrating an exemplary hardwarearchitecture of a computing device used in an embodiment of theinvention;

FIG. 21 is a block diagram illustrating an exemplary logicalarchitecture for a client device, according to an embodiment of theinvention;

FIG. 22 is a block diagram showing an exemplary architecturalarrangement of clients, servers, and external services, according to anembodiment of the invention;

FIG. 23 is another block diagram illustrating an exemplary hardwarearchitecture of a computing device used in various embodiments of theinvention;

FIG. 24 is a flow diagram illustrating an exemplary process forexporting fixed-layout content items and associated data stores,according to an embodiment of the invention;

FIG. 25 is a flow diagram illustrating an exemplary process for findingand automatically configuring element areas (single areas and arearanges) that are outlined on or in fixed-layout content items andassociated data stores, according to an embodiment of the invention;

FIG. 26 is a flow diagram illustrating an exemplary process for findingand configuring each element area or an adjacent range of element areas,according to an embodiment of the invention;

FIG. 27 is a flow diagram illustrating an exemplary process forautomatically finding an element area dimensions inside a figure outlinewhich is embedded in a fixed-layout content item, or for layersadditional object areas, according to an embodiment of the invention;

FIG. 28 is a block diagram illustrating an exemplary process forretrieving and displaying fixed-layout components as part of overallapplication systems, according to an embodiment of the invention.

DETAILED DESCRIPTION

The inventor has conceived, and reduced to practice, systems and methodsof programmatically generating and managing a plurality of embeddedfixed-layout components and associated items into a display component ofa computer system user interface.

One or more different inventions may be described in the presentapplication. Further, for one or more of the inventions describedherein, numerous alternative embodiments may be described; it should beappreciated that these are presented for illustrative purposes only andare not limiting of the inventions contained herein or the claimspresented herein in any way. One or more of the inventions may be widelyapplicable to numerous embodiments, as may be readily apparent from thedisclosure. In general, embodiments are described in sufficient detailto enable those skilled in the art to practice one or more of theinventions, and it should be appreciated that other embodiments may beutilized and that structural, logical, software, electrical and otherchanges may be made without departing from the scope of the particularinventions. Accordingly, one skilled in the art will recognize that oneor more of the inventions may be practiced with various modificationsand alterations. Particular features of one or more of the inventionsdescribed herein may be described with reference to one or moreparticular embodiments or figures that form a part of the presentdisclosure, and in which are shown, by way of illustration, specificembodiments of one or more of the inventions. It should be appreciated,however, that such features are not limited to usage in the one or moreparticular embodiments or figures with reference to which they aredescribed. The present disclosure is neither a literal description ofall embodiments of one or more of the inventions nor a listing offeatures of one or more of the inventions that must be present in allembodiments.

Headings of sections provided in this patent application and the titleof this patent application are for convenience only, and are not to betaken as limiting the disclosure in any way.

Devices that are in communication with each other need not be incontinuous communication with each other, unless expressly specifiedotherwise. In addition, devices that are in communication with eachother may communicate directly or indirectly through one or morecommunication means or intermediaries, logical or physical.

A description of an embodiment with several components in communicationwith each other does not imply that all such components are required. Tothe contrary, a variety of optional components may be described toillustrate a wide variety of possible embodiments of one or more of theinventions and in order to more fully illustrate one or more aspects ofthe inventions. Similarly, although process steps, method steps,algorithms or the like may be described in a sequential order, suchprocesses, methods and algorithms may generally be configured to work inalternate orders, unless specifically stated to the contrary. In otherwords, any sequence or order of steps that may be described in thispatent application does not, in and of itself, indicate a requirementthat the steps be performed in that order. The steps of describedprocesses may be performed in any order practical. Further, some stepsmay be performed simultaneously despite being described or implied asoccurring non-simultaneously (e.g., because one step is described afterthe other step). Moreover, the illustration of a process by itsdepiction in a drawing does not imply that the illustrated process isexclusive of other variations and modifications thereto, does not implythat the illustrated process or any of its steps are necessary to one ormore of the invention(s), and does not imply that the illustratedprocess is preferred. Also, steps are generally described once perembodiment, but this does not mean they must occur once, or that theymay only occur once each time a process, method, or algorithm is carriedout or executed. Some steps may be omitted in some embodiments or someoccurrences, or some steps may be executed more than once in a givenembodiment or occurrence.

When a single device or article is described herein, it will be readilyapparent that more than one device or article may be used in place of asingle device or article. Similarly, where more than one device orarticle is described herein, it will be readily apparent that a singledevice or article may be used in place of the more than one device orarticle.

The functionality or the features of a device may be alternativelyembodied by one or more other devices that are not explicitly describedas having such functionality or features. Thus, other embodiments of oneor more of the inventions need not include the device itself.

Techniques and mechanisms described or referenced herein will sometimesbe described in singular form for clarity. However, it should beappreciated that particular embodiments may include multiple iterationsof a technique or multiple instantiations of a mechanism unless notedotherwise. Process descriptions or blocks in figures should beunderstood as representing modules, segments, or portions of code whichinclude one or more executable instructions for implementing specificlogical functions or steps in the process. Alternate implementations areincluded within the scope of embodiments of the present invention inwhich, for example, functions may be executed out of order from thatshown or discussed, including substantially concurrently or in reverseorder, depending on the functionality involved, as would be understoodby those having ordinary skill in the art.

The following description is presented to enable any person skilled inthe art to make and use the present invention, and is provided in thecontext of various embodiments and their requirements. Variousmodifications to the disclosed embodiments will be readily apparent tothose skilled in the art, and the general principles defined herein maybe applied to other embodiments without departing from the spirit of thescope of present embodiments. Thus, the invention is not limited to theembodiments shown, but the present embodiments are to be accorded thewidest scope consistent with the principles and features disclosedherein.

The disclosed technology and methods addresses the need in the art forcreating and utilizing fixed-layout component package(s) which can thenbe embedded in the overall programmatic user device interface to createone overall interaction for the user. Certain embodiments of the presentinvention relate to how fixed-layout display component(s) can becreated, embedded and managed across a wide range of user devices anddevice types, and where these component(s) may be displayed consistently(e.g. aspect ratio, positioning, display layer sequence etc.)irrespective of the device type and orientation, and which isindependent of the overall programmatic display user interface. The usercan interact with data elements which may be contained within thefixed-layout component and which are linked positionally to theunderlying fixed-layout component layout area via the defined componentspecific data. The fixed-layout area component may be resized andrepositioned across any device or orientation and where the component(s)may then display in a same consistent manner irrespective of the devicescreen size or orientation or user viewing area.

FIG. 1A illustrates an exemplary user device screen detailing theprogrammatic display area and an embedded fixed-layout componentdisplay, according to an embodiment of the invention. According to theembodiment, device overall display area 100 may comprise fixed-layoutdisplay area component 102, and an area of screen 103 which is generatedprogrammatically. The resulting overall user interface may be acombination of fixed-layout component(s) and programmatic elements.

FIG. 1B illustrates an exemplary user device screen detailing the devicescreen 104, the programmatic display area 110, and a number of embeddedfixed-layout components 106, 107, 108, 109 displayed, according to anembodiment of the invention.

FIG. 2A illustrates an exemplary expanded view of a fixed-layout displaycomponent, according to an embodiment of the invention. According to theembodiment, fixed-layout display component 102 may be an enlarged viewof 102 (referring to FIG. 1A). This fixed-layout component 102 maycomprise fixed-layout component elements; area 201, and any number ofassociated fixed-layout element item 202, 203, 204, 205, 206, 207, 208.The fixed-area component element areas 202, 203, 204, 205, 206, 207,208, may be fixed positionally relative to the overall area of componentarea 201, and therefore relative to all the other component elementsreferenced. The fixed-layout element areas may be contained within thefixed area content item 201, or any programmable shape area, includingrectangles, triangles, circles, and/or other shapes which may beoverlaid on top of area 201. Each fixed-layout element area 202, 203,204, 205, 206, 207, 208 may comprise one or many content items (e.g.images). The component area 201 which is visible (that is, not hiddenfrom view by the element areas) can have a programmable generated userinteractivity (e.g. data text entry, selection, etc.). Elements areas202, 203, 204, 205, 206, 207, 208 may have a plurality of programmablegenerated user interactivity associations. Programmable interactivitiesallows additional functions on overall component area 201 or on anyelement 202, 203, 204, 205, 206, 207, 208 which may be associated withthe overall component 102, or any combination thereof.

FIG. 2B illustrates another exemplary view of a fixed-layout displaycomponent, according to an embodiment of the invention. According to theembodiment, fixed-layout component 102 (referring to FIGS. 2A and 2B)may be an enlarged view of 102 in FIG. 1A. The component 102 maycomprise fixed-layout component area 201, which may comprise any numberof fixed-layout element items 211, 212, 213, 214. According to theembodiment, the fixed-layout element items 211, 212, 213 may bepartially overlapping with each other. Each fixed-layout area (that is,the overall area 201, and elements 211, 212, 213, 214) may each beassociated with relevant display-layer identifier data. Thedisplay-layer identifier data may be used when the overall fixed-layoutcomponent is being displayed in a user device screen 101 (referring toat least FIG. 1A) to determine the display order or sequence of thevarious areas for display within the component. The display-layeridentifier data may determine areas that may be visible on an interfacedisplay (for example, of a user device) and which may be partially orfully hidden from direct view (for example, by a user via the userdevice), as illustrated in FIG. 2B. Further according to the embodiment,overall area 201 may have, for example, a display-layer identifier=1,and area 213 and 214 may have, for example, a display-layeridentifier=same as each other=2, and area 212 may have, for example, adisplay-layer identifier=3, and area 211 may have, for example, adisplay-layer identifier=4.

Dimensions General Definition

In some embodiments, all dimensions relating to a fixed-layout componentmay be related to “digital-imaging” or “digital-content” and may bemeasured or represented in a pixel, pel, dots or picture element orother related methods for dimensions. These measurement types may, insome embodiments, relate to a physical point in a raster image, or to asmallest addressable element. For convenience, the term “pixels” as theexemplary definition of a dimension will be used hereinafter, but notingthat a wide range of other methods may also be used to achieve a similaror the same result.

For convenience, pixels may be normally arranged in a regulartwo-dimensional grid. The location of co-ordinates address (or otherexemplary method) of a pixel will correspond to its physical coordinateswithin this dimensional area. All dimensions referenced will relate to atwo-dimensional view.

FIG. 3 illustrates an exemplary definition of dimensions of a pluralityof fixed-layout component according to an embodiment of the invention.According to the embodiment, fixed-layout component 102, fixed-layoutcomponent are 201, detailing width 301 and height 302 dimensions may beused to derive a fixed-layout component aspect-ratio (dimension width301 divided by dimension height 302) and which may always be used in thedisplay/redisplay of this fixed-layout component area across anydevice/screen and to ensure that the calculated aspect-ratio is what mayalways be displayed in user device screen 101, irrespective of theactual aspect ratio or orientation of a physical screen associated touser device 101.

FIG. 4 illustrates an exemplary definition of dimensions of a pluralityof element items that may be part of a fixed-layout component display,according to an embodiment of the invention. According to theembodiments, fixed-layout component 102, with the fixed-layout componentarea 201. FIG. 4 further illustrates component element fixed area 207detailing element width 401 and element height 402 dimensions and whichmay be used to derive a component element aspect-ratio (that is,dimension width 401 divided by height 402) which may be used indisplay/redisplay of this fixed-layout element across any device/screenas part of specific fixed-layout component 102.

FIG. 5A illustrates an example of positional two dimensions (2D) of anelement area 207 in relation to a defined reference location 509 on anoverall fixed-layout component area, according to an embodiment of theinvention. According to the embodiment, an exemplary method to calculatethe dimensional data for elements within a component and which measurethe elements size and position precisely in relation to the overallcomponent area 201 is shown. According to the embodiment, an exemplarymethod to use 2D dimensional x and y axis methodology to determinespecific x-y coordinates is also presented.

In FIG. 5A, the fixed-layout component reference point 501 may be anyfixed location associated to component area 201. Component area 201 mayhave associated dimension x-Axes 502 and y-Axes 503 and direction.Accordingly, each fixed-layout element may have an associated referencepoint in a two-dimensional dimension display grid which may have anx-Axis 502 and a y-Axis 503. Each Axes may each have dimensional valuesfrom 0, 1 (506) to “n” (507) as for the x-Axis and from 0, 1 (504) to“n” (505) as shown for the y-Axis. Each dimension point will have an xand y dimension pair value in the x-y two-dimensional dimension grid.Further according to the embodiment, element area 207 may haveassociated reference point 509 displayed which may have a unique x and yco-ordinate pair values for dimension position. In this embodiment, thecomponent reference point 501 can have a position of 0, 0 for the x, ydimension's pair. Element 207 may be positionally and dimensionallyrelated to the component reference point 501 via the element referenceheight 508 and the element reference width 510 dimensions. The element207 may have a fixed dimension size for width and height 401, 402 andposition 508, 510 relative to the overall component area 201, and withsize/area 301, 302. All of these dimension values can be derived fromthe corresponding x and y co-ordinate position pair dimension values ofall corner points (known as “element area definition positions”) for theoverall component area and associated element areas (for the elementtype shown: rectangle areas). The x and y coordinate values for theelement area 207 corner points 509, 511, 512, 513 may be used to derivethe element width and height dimensions as well as area and the positionof the area relative to the overall fixed-layout component area. Itshould be understood by those with ordinary skill in the art thatalternate methods may be used to arrive at the same feature,functionality, or conclusion.

FIG. 5B illustrate an exemplary variation of positional dimensions of anelement in relation to a defined reference location on an overallfixed-layout component area, according to an embodiment of theinvention. According to the embodiment, an exemplary variation of FIG.5A is shown with respect to the y-Axis dimension 511 orientation, ascompared to the y-Axis 503 as demonstrated in FIG. 5A. However, theremay be many other different approaches to measuring the variousdimensions required to deliver a same required result of maintaining thepositional and area and size integrity of all items relative to eachother, and in relation to the overall component area, and which are partof each specific fixed-layout component 201.

FIG. 6A illustrates an example of a reference position location for aplurality of elements and a reference position location for the overallfixed-layout component area, according to an embodiment of theinvention. According to the embodiment, how each element reference point502, 601, 602, 603, 604, 605, 606 may be connected, and referenced backto the component reference point 501 via the reference height 503, andreference width 504 of each element may be shown.

FIG. 6B illustrates an example of a different reference positionlocation for a plurality of elements and a reference position locationfor the overall fixed-layout component area, according to an embodimentof the invention. According to the embodiment, element reference points607, 608, 609, 610, 611, 612, 613 may be positioned centrally in eachcomponent element. It should be understood by those experienced in theart that alternate methods could be used to arrive at the same feature,functionality, or conclusion.

FIG. 7A illustrates an example of interactivities (including displayproperties) provided by the element areas to an embodiment of theinvention. According to the embodiment, example element areas 203, 207may be associated with element user interface interactivity functions.These areas allow interaction from a user device (for example, via inputfrom a touchscreen, mouse click, etc.). These user interfaceinteractivity functions may support a wide range of input, such as usertext data entry 701, 702, which may uniquely be linked to the respectiveelement area 203, 207. According to the embodiment element areas 703 and704 could display different display colors to the user-device, and/or beassociated with multiple states for each specific element.

FIG. 7B illustrates an example of “element area definition positions”according to an embodiment of the invention. According to theembodiment, the element area 207 may have a number of “unique elementarea definition points” 706, 707, 708, 709 whereby each elementdefinition point may have a unique x and y dimension co-ordinate value.The calculation of these values allows the creation of an interactiveelement area which can occupy this element area 207. The x and ydimension coordinates can then be used to calculate all the otherpreviously referred dimensions: 401, 402 508, 510, which then allows thecalculation of relative positional data for this element area 207relative to the overall fixed-layout component area 201.

FIG. 8 illustrates an example of the various data stores (database,metadata, files, etc.) associated with one or more fixed-layout areadisplay components, according to an embodiment of the invention.According to the embodiment, fixed-layout component 102, and with theoverall area 201, may be understood to be a, “background,” area of anoverall component relative to the element areas 202, 203, 204, 205, 206,207, 208 which may be visible in a, “foreground,” in a relative sense.FIG. 8 further illustrates each fixed-layout component (all backgroundand foreground areas) may have associated graphics, digital images,multimedia, or other data associations 801. FIG. 8 further illustratesall the dimensional, positional, calculated, relative, layer data, file,and metadata 802 and element user interactivities function associationdata 803 and other display, state, color and related associated data804. All this data and associated metadata and files and any derived orfurther calculated data linking all these data items to the overallfixed-layout component, including the elements, are assembled, andstored in the component definition data store 806.

FIG. 9 is a high-level flow diagram illustrating an exemplary processfor calculation of all dimension data for items (e.g. element areas)which may be part of a fixed-layout component area, according to anembodiment of the invention. According to the embodiment, a fixed-layoutcomponent package preparation method is depicted. Accordingly, a userdevice may initiate component package definition process 901 byanalyzing and preparing an overall component area and any associatedgraphics or digital image(s) for component background area 201, analyzea plurality of defined areas assigned to each associated element, andprepare any graphics or digital images associated with the element(s)902 as part of the overall component. The primary dimensions 301, 302,401, 402, 503, 505 for the overall area and each element(s) 202, 203,204, 205, 206, 207, 208 are calculated in step 903. All of these primarydimensions may be processed further 904 resulting in derived calculateddimensions to support the requirement that all items in the overallfixed-layout component can support dynamically scaling and repositioningof the overall component size and associated elements so that accuratepositional, size and display integrity is maintained. All thedisplay-layer data (referring, for example, to the system of FIG. 2B)user interactivities types, different user states, and display colors,may be associated with each specific elements or overall componentarea(s) as required in step 905. All the dimension data (primary andcalculated, derived) are then stored in the dimension's metadata datastore 802. If elements have associated user interactivities 905 thisdata may be assembled and stored in the component package definition 803data store. All of the relevant data items for the overall component maythen be finally assembled 906 from the various data sources 801 802 803804 and may be placed 907 in each component definition data store 806.The method step 901 may be repeated for all components which require thedata definition.

Fixed Area Programmatic Display Window

FIGS. 10A and 10B illustrate an example of a fixed area programmaticdisplay window which may be part of the overall user display window in adisplay screen, according to an embodiment of the invention. Accordingto the embodiment, a programmatically generated window area 1001, withpositional dimensions 1002 1004, and with area size dimensions 1003 and1005 may be shown. The position and size of this display window will becontrolled programmatically as part of an overall programmatic userinterface application on the user device. The fixed-layout component 102will be programmatically placed inside 106, 107, 108 the display window1001 and resized dynamically to fit within this actual display windowsize, while also maintaining the aspect ratio of fixed area component102, and all the elements contained within the fixed-layout package, andthe relative size, position and display-layer data of all elementsrelative to each other as part of the overall component package. Furtheraccording to the embodiment, component 102 may be placed inside displaywindow 1001 where the width of the component may be dynamically resizedto equal the width of the display window 1001, and where there the depthof the component may be less than the display window resulting in anexcess space area 1009. Further according to the embodiment, the aspectratio of the programmatic display component 1001 may have the sameaspect ratio as the fixed-area component area 201, which would enablethe fixed-area component to exactly “fit into” this programmatic displaywindow 1001. Display layer metadata may be used to ensure that all areasare shown to the user in the correct predefined sequence, and where somemay overlap others ref FIG. 2B. The programmatic window 1001 may beresized and repositioned dynamically in FIG. 10C the updated window sizeand position 1010, driven by specific user interactivities with theoverall programmatic application. The fixed-layout component 102 willthen dynamically resize to fit new window area 1010, while alsomaintaining the aspect ratio of the fixed area component 102, and theelements contained therein, and that the relative size, position anddisplay-layer data of elements relative to each other may be maintainedas part of the overall fixed-layout component package.

FIG. 11 illustrates a plurality of exemplary fixed-layout windows and acomponent contained therein as it is repositioned and automaticallyresized in various device screens display sizes, according to anembodiment of the invention. According to the embodiment, user interfacescreen 101, 1101, 1103, 1105, 1107 of a plurality of user devices aredepicted. Each user interface may comprise programming instructionsstored in the memory, the programming instructions, when executed by theprocessor may display the overall application to the user. Thefixed-layout content may display independently within the fixed areadisplay window provided FIG. 11: 102, 1102, 1104, 1106, 1108, as part ofeach device display screen 101, 1101, 1103, 1105, 1107. The fixed-layoutarea can be re-sized, re-scaled and repositioned independently anddynamically depending on end user requirements and the overallprogrammatic screen display logic.

FIG. 12 illustrates various examples of user devices 1201, 1202, 1203,and each containing a programmatic display window 1204, 1205, 1206, andwhere the fixed-layout component may be automatically resized to fiteach provided programmatic display window, while maintaining allpositional, dimensional and aspect ratios within the fixed-layoutcomponent. According to the embodiment, the positioning of fixed-layoutcontent display 102 in one specific (same) device 1201, thenrepositioned in the same device 1202 in the same specific orientationand with different device orientation detailed in 1203. As the deviceorientation may be changed from “Portrait” 1201 and 1202 to “Landscape”1206 the fixed-layout component can be dynamically repositioned andresized as a unified component within a changing programmatic displaywindow 1204, 1205, 1206.

FIG. 13 details an example of a client device 1300 with an onlineapplication installed 1301 and communicating over a network 1306 with aserver application 1307. In this embodiment which details the exampleonline user interface module(s) 1302 which may reside on the clientdevice 1301. The online user interface module 1302 can be an integralpart of the user interface modules 1308, and which may be a component ofthe overall server system 1307.

The user client device(s) 1300 may communicate directly or indirectlywith the server 1307 and other systems via network(s) 1306. Deviceapplication 1301 user interface module 1302 may comprise programmaticcomponent 1303 and fixed-layout display UI component 1304. Online deviceuser-interface modules 1303, 1304 may be downloaded/synchronizedautomatically on use from the application server modules 1309, 1310.Programmatic client interface module 1303 may manage all aspects of theuser display and for programmatic generated content and activities, andthe creation, positioning, re-positioning and management of the fixedarea display window 1001 (referring to FIG. 10A). Fixed-layout componentmodule 1304 may manage aspects of the fixed-layout display componentsand any associated end-user generated data 1313. This module may accessthe specific component package(s) for the component(s) being displayed,it may then read the component definition data store 806 and thenprocess all the contained data, render and display the package(s) withinone or more fixed windows 1001 (referring to FIG. 10A) supplied byprogrammatic client interface module 1304 and present that to the enduser on the device screen. If associated user data exists this will thenbe accessed from the user data store 1313 and also presented to theuser.

While the client device 1300 and online application server system 1307are presented with specific components, it should be understood by oneskilled in the art, that the architectural configuration of the system1300, 1307, 1312 may be simply one possible configuration and that otherconfigurations with more (or less) components are also possible toachieve the desired result.

FIG. 14 details an example of a client or user device 1401 with aninstalled or “native” application (hereinafter referred to as “APP”)1402, and which communicates over networks 1410 with the ServerApplication 1307. The user client device(s) 1401 may communicate bothdirectly and/or indirectly with the server 1307 and other systems 1408via the network(s) 1410. The original installation of the “native”application on the device may be provided from application deliveryserver 1408. APP 1402 installation module or program 1409 may providethe application installation files from data store 1410, and this datastore may also contain a version of component definition data 806 forthe fixed-layout component definitions. When the initial installationhas completed a copy of the component definition data 806 may then alsoreside with or inside APP 1402 on actual user device 1401. Componentpackage APP data store 804 inside APP 1402 may also receive subsequentautomatic or ad-hoc updates from a different or updated version of thisdata file which may be stored on the online application server system1307 or the application delivery server 1408.

Installed APP 1402 and online client software 1301 may both existseparately and may be independent of each other on any specific samedevice 1300, 1401. APP 1402 user interface module may comprise its ownprogrammatic component module 1404 and fixed-layout component module1405. APP 1402 programmatic client interface module 1404 may manageaspects of the user display and for programmatic generated content andinteractivities and the creation, positioning, re-positioning andmanagement of fixed area display window 1001 (referring to FIG. 10A).The fixed component module 1405 may manage aspects of the fixed-layoutdisplay components and any associated end-user generated data 1407. Thisfixed-layout component module 1405 may access a specific version of thecomponent definition data 806 inside or directly associated with APP1402 for the component being displayed (within APP 1402). Fixed-layoutmodule 1405 may then read from the component definition data store 806and then process all the contained data, render, and display thefixed-layout package within the fixed display window 1001 supplied byprogrammatic client interface module 1404 and display that to the enduser device. If user data 1407 which may be associated with APP 1402,the fixed-layout component module will also then retrieve and displayAPP data 1407 for the user via fixed-layout module 1405.

The user may interact with the fixed element areas 202, 203, 204, 205,206, 207, 208 as part of specific component 201. Where these fixedelement areas are configured to receive user-entered data 701 and 702,whereby this data may be saved to APP data store 1407 via theapplication logic modules 1406. If the user element data is already indata store 1407 (within the APP 1402, for example, from a previous save)it may be displayed/redisplayed to the associated user interface oncompletion and display of the fixed-layout component. Application (APP)user data store 1407 can update (as required) online application serversystem 1307 user data store 1313 via the server application programminginterface (API) module 1311.

While client device 1300, 1401 and server systems 1307, 1408, arepresented with specific components, it should be understood by oneskilled in the art, that the architectural configuration of the system1401, 1408, 1307 may be simply one possible configuration and that otherconfigurations with more (or less) components are also possible toachieve the desired result.

FIG. 15 is a high-level flow diagram illustrating an exemplary processfor programmatically loading and displaying a plurality of fixed-layoutcomponents, according to an embodiment of the invention. According tothe embodiment, user device software (online 1301, or native/installedapp 1402) software load and display process 1500: In some embodiments,the device display software 1302, 1403 may load programmatic module1303, 1404 and may then complete initial initialization 1501 for a userdevice display. If a user device display comprises fixed-layoutcomponent 1502, programmatic device interface module 1303, 1404 mayinitialize 1503 viewing display window 1001 for the fixed-layoutcomponent. Fixed-layout component device interface module 1304, 1405 maythen access the specific component 1504 from the component data store804, where all the data may then be processed 1505 and the fullyassembled/rendered fixed-layout package containing all its associateditems may be then presented to the display window 1001 in step 1506,while dynamically resizing as required. If end-user data 1313, 1407exists and is associated with the specific fixed-layout component beingdisplayed, this data may be retrieved and displayed 1507 to the user bythe modules 1304, 1405. Device application load and display process 1500may be repeated from step 1502 for all fixed-layout components which maybe part of the device screen (referring to FIG. 1B).

FIGS. 16A and 16B illustrate an exemplary embodiment of a fixed-layoutcomponent combined with programmatic display elements on a screen of auser device with a plurality of orientations, according to an embodimentof the invention. According to the embodiment, support for multipleorientations of landscape 1601 and portrait 1606 may be shown. The userdevice 1601, 1606, details the display 1602, 1607, whereby programmaticdisplay area 1603, 1610 may be shown, and in contrast the fixed-layoutarea 1604, 1608 may be also shown. Further according to the embodimentprogrammatic text 1603, 1610 and fixed-layout component 1604 may bedisplayed. Programmatic text 1603 can be user selectable, whereas fixedcomponent text 1604, 1608 may be non-selectable and may be contained,for example, on the fixed-layout area background digital graphic, andwhere the scaling may determine the text size of the fixed-layoutcomponent package within the window 1001 (referring to FIG. 10). Anexample of a user interactivity element is detailed in 1605, 1609,whereby its position and function are managed by the fixed componentmodules 1304, 1405 and may be independent of the overall programmaticapplication modules 1303, 1404. Display window 1001 size and positionmay be different across the device orientations 1601 and 1606 which mayresult in different size scaling of the fixed-layout component.

FIG. 18 illustrates an exemplary embodiment of a fixed-layout contentcomponent item 102 that comprises element areas 1801, 1802, 1803, 1804,1813, 1815, 1817 that may be contained in/on fixed-layout content item201, and that may form a basis for new element items 1808, 1809, 1807,1814, 1816, 1818 (for example, as defined in FIG. 2A: 202, 203 . . .208). Element area items 1808, 1809, 1807, 1814, 1816, 1818 may beautomatically derived from highlighted areas 1801, 1802, 1803, 1804,1813, 1815, 1817. Newly derived and calculated element areas 1807, 1808,1809, 1810, 1814, 1816, 1818, are operable to support additional userinteractivities.

FIG. 18 further illustrates an exemplary fixed-layout content item area208 that may be defined as a “background” area 208 relative to anyelement areas 1801, 1802, 1803, 1804, 1813, 1815, 1817, that may be in a“foreground” on a relative basis (in some embodiments this may be seenas a layer). Further according to the embodiment, fixed-layout component102 may comprise fixed-layout content item area 208, any number ofdigital graphics (for example, to makeup the full or partial area 208),items such as text, pictures, shapes, and four highlighted outline areas1801, 1802, 1803, 1804, 1813, 1815, 1817 may be embedded as part ofcontent item area 208. An overall objective, in a preferred embodiment,may be to automatically find and create element item areas (as definedin FIG. 2A: 202-208, etc.) which may be based on highlighted exemplaryareas 1801, 1802, 1803, 1804, 1813, 1815, 1817. Further according to theembodiment, new element item areas 1807, 1808, 1809, 1810, 1814, 1816,1818, may be dimensionally sized and positionally located such that theelement item areas may reside just within these exemplary highlightedareas 1801, 1802, 1803, 1804, 1813, 1815, 1817. An objective istherefore to automatically identify a plurality of areas (that is, aplurality of “automatically found and calculated” areas) which may beinside each of areas 1801, 1802, 1803, 1804, 1813, 1815, 1817. These“automatically found” item areas comprising dimensional, positional, anddisplay-layer data may then be each added as new “element items” tofixed-layout component definition data 806 (referring to FIG. 8).

Further according to the embodiment, a process is disclosed that may“automatically find” and calculate element item areas 1807, 1808, 1809,1810, 1814, 1816, 1818, which are the dashed line figure area inside thehighlighted area 1801, 1802, 1803, 1804, 1813, 1815, 1817, asillustrated. It should be noted that the “automatically found” elementitem areas illustrated 1807, 1808, 1809, 1810, 1814, 1816, 1818, (dashedline figure) may be marginally smaller than the highlighted area 1801,1802, 1803, 1804, 1813, 1815, 1817 identified as part of the backgroundimage.

In other embodiments an “automatically found” area be can equal to orgreater than (or much less than) highlighted areas 1807, 1808, 1809,1810, 1814, 1816, 1818. “Automatically found” element definition points706, 707, 708, 709 coordinates may then be used to further derivedefinition data required in the 802 dimension and positional data storewhich can then support a final assembly of fixed-layout componentdefinition data 804. There may be many other alternative methods todetermine element definition points 706, 707, 708, 709 coordinates tocalculate width 401, height 402, and position of all element areasrelative (as in FIG. 5: 508, 510) to the overall fixed-layout contentitem. “Automatically calculated” element item areas 1807, 1808, 1809,1810, 1814, 1816, 1818 (dashed line figure) may be pre-defined as apercentage smaller than the boundary of the highlighted area 1801, or itmay be a same size or also larger, depending on the requirement orconfiguration.

FIG. 19 is a high-level flow diagram illustrating an exemplary processfor an automatic finding and calculation of element item areas andassociated data for data stores, according to an embodiment of theinvention. According to the embodiment, an example of process flow stepsfor “automatic finding and calculation” of element item areas and allassociated data for component definition data 806 (referring to FIG. 8)is shown. Process 1900 starts at step 1901 to automatically find andcalculate the fixed-layout element item areas and associated data andthen to provide the data (and derived data) which may be required fordimensions and positional data store 802 and which may then be used infinal fixed-layout package data store 806. An alternative may be for theuser to manually calculate the necessary dimensional and positional data806. The process is started 1901 by the initialization 1902 of a “searchapplication” (which can be either an online application or anative/installed application) and where the overall fixed-layoutcomponent item 208 may be loaded and displayed to a user. The user canthen select if a single element item area must be identified or ifmultiple adjacent areas 1801, 1802, 1803, 1804, 1813, 1815, 1817 in step1903 are to be identified. The user may then commence a single elementarea search by selecting an “area specific” physical location, any pointlocation 1805 inside the area 1801 via input received from a computermouse pointer or finger touch control or other device input method. Inarea 1801, the search algorithm may then commence the search in manydirections 1803, 1804, 1805, 1805 to determine calculations datanecessary to support the new calculated area perimeter of 1807 (thedashed line figure). All the data and calculated/derived data for thespecific area 1807 may be saved to the dimensions and position datastore 802. If a search for a single area was initiated initially, thenthe search process may be completed. If a search for multiple adjacentareas was initiated (referring embodiment areas 1802, 1803, 1804 or1813, 1815, 1817), then step 1907 continues processing at step 1905where the search algorithm may move automatically onto the nextassociated adjacent area (in this embodiment 1803 and 1804, or 1815 and1813, 1804, etc.) and identify all the required data where it may all besaved in the dimensions and positional data store 802. For multipleadjacent area search, the user may then commence the search by selectingan “area specific” physical location, any point location 1812 inside thearea 1802 via input received from a computer mouse pointer or fingertouch control or other device input method, and selecting the generalsearch direction 1811 for the automatic search. The general searchdirection defines the general direction of a search (for adjacentcells), and can be in a specific direction from a start point; left,right 1822, up, down 1811, etc. A general search direction can also beset automatically so that all the possible directions (up 1824, down1811, left 1823, right 1822) may checked automatically to identify allthe adjacent cells in each specific cell direction.

In area 1802, the search algorithm may then commence the search withinthat area firstly (in the same way as outlined for area 1801 above) todetermine calculations for that first element area, and then for thealgorithm to progress in the defined direction 1811 to define elementareas 1803 and 1804 in this illustrated embodiment. This iterativeprocess 1908 for multiple element areas will continue until all adjacentareas are processed and the iterative process ends 1909 and all the datais processed and stored in the element area dimensions data store 802,which is then processed further to create the final fixed-layoutcomponent definition data 806.

Fixed-Layout Component Creation

FIG. 24 is a block diagram illustrating an exemplary system architecture2400 for creating the fixed-layout component packages, according to apreferred embodiment of the invention. According to the embodiment,creation of fixed-layout components may comprise: fixed-layout contentexport parameters designator 2403 may designate a quality (for example,a level of image pixilation, image grain, and the like), resolution (forexample, a high or low number of pixels), and file size (for example,kilobyte (kB)/megabyte (MB), etc.) of a fixed-content component, priorto the actual creation of fixed-layout components. User devices 2401 a-nmay receive, send, and set parameters associated to fixed-layout contentvia accessing export parameters designator 2403 via, for example, cloudnetwork 2402 (or FIG. 22 network 31), prior to export manager 2404importing, processing, and exporting fixed-layout content items (forexample, a selection of fixed-content filed resident on storage deviceHDD 52 imported from the file system, and processed by system 2400).Fixed-layout content export manager 2404 may import source files(s) in aplurality of source formats known in the art (e.g. PDF, Microsoft™ Worddocuments, and the like) that may comprise a plurality of pages, andthen analyze and export each fixed-layout content item (e.g. afixed-content layout graphic such as PNG, JPEG, and the like).Accordingly, the fixed-layout content export process may result in oneor more associated items (e.g. PNG, JPEG, and the like) for each page ofthe plurality of pages of the original source file. Interaction requestsfrom one or more user devices 2401 a-n may be received by export manager2404 to: identify one or more input files (for example, PDFs); toprocess and start an automatic process of importing the input files(i.e. “the PDFs”) and exporting the components (i.e. “the PNGs”).Content metadata manager 2405 may receive exported files from exportmanager 2404 and create associated additional metadata to the exportedfixed-layout item.

Element finder 2406 may automatically find dimensions of a single shapearea or a range of adjacent areas for areas embedded in the fixed-layoutcomponent item which has been exported via export manager 2404 (e.g.PNG, JPEG, etc.). Interaction requests may be received from one or moreuser devices 2401 a-n by export manager 2404 to, for example, select atwo-dimensional (2D) area for where element finder 2406 may commence asearch for one or more shape areas. Element metadata manager 2407 mayreceive one or more 2D x-y coordinates data from element finder 2406 andperform calculations on this data (for example, as described in FIG. 5,FIG. 10, FIG. 18). Element creator 2408 may allow a creation ofareas/shapes that may be an overlay displayed on top of the fixed-layoutexported content component item. For example, as an additional layer ofinteractive components directly associated to the fixed-layout contentwith associated functions. File loader 2409 may upload exported filesfrom a storage device (such as HDD 52), for example, upon receiving arequest and location from a user device 2401 a-n, and place them intosystem 2400 for further processing by client metadata module 2405. Fileviewer 2410 operates as a mechanism to view files, as is known in theart. All fixed-layout exported content which is generated by the exportmanager 2404 and the content metadata manger 2404 may be saved to thefixed-layout exported content and metadata data store 801. All fixedlayout element definition data (metadata, calculated, etc.) may be savedto the element all data store 805

In some embodiments, at least system components 2403 . . . 2410 mayreside and execute completely on a user device 2401 a in one completesystem.

FIG. 25 is an exemplary process for creation of an exported fixed-layoutcontent item, database, and files 801. According to an embodiment, agraphic file/image (e.g. PNG, JPEG, etc.) may be exported from a sourcefile (for example, a PDF file). According to the embodiment, for n pagesin the source file, the export may provide n number of graphic/files(e.g. PNG files) export files. In some embodiments, any number ofgraphic/files may be exported for a single PDF page such that thesegraphics can be re-assembled dynamically (or using tiling techniques, orsimilar methods)) into one overall seamless graphic presented to adisplay of, for example, user device 2401 a, such that an end user maynot be aware that the graphic presented may be a range of smaller filesdynamically presented together to give a seamless and unified view ofthe original PDF page. Accordingly, a request to commence process 2501may be received from, for example, user-device 2401 a.

Accordingly, in step 2503, a request from user-devices 2401 a-n may bereceived, at files viewer module 2410, to organize at least a portion ofone or more fixed-layout content source files 2502 into a fixed-layoutbatch source content location 2504 and non-batch 2508 source contentfiles. A “batch” of fixed-source content files may refer to a groupingof files in a location in a file management system such that thegrouping of files may be loaded as a group or “batch” and where thegrouping may be processed automatically, for example, one by one, untilall files in the “batch” are processed. Examples of “batch” content filetypes may include, but not limited to, Adobe™ PDF files, Microsoft™ WordDOCX (DOC and other variants) and image types, such as, PNG, JPEG, TIFF,and the like. Examples of “non-batch” content files may include, but notlimited to, Adobe™ Photoshop™ (PSD), Adobe™ InDesign™ (IDD), CorelDraw™(CDR), and the like.

In a next step 2505, export parameters designator 2403 may configuresystem 2400 to define required parameters on content export (forexample, at least quality, resolution, color, and other parameters asdescribed earlier). Export parameters designator 2403 may receive one ormore requests from, for example, user devices 2401 a relating toparameters which needs to be set, such as, viewing quality (e.g. sharpor grainy (“pixelated”) text on a graphic, which may be a function ofpixel resolution and other parameters) of the fixed-layout component,which in turn may relate to dimensions and resolution (pixels size widthby height) of the exported content component. The quality parameters mayresult in varying file sizes (kB, MB, etc.) of the files that areexported. Once step 2505 is complete, an automatic content exportprocessing step 2506 may be initiated by, for example, a request fromuser device 2401 a. Accordingly, content export manager 2404 may receivea request from one or more user devices 2401 a-n to load one or moresource file from the fixed-layout source content files 2504. Contentexport manager 2404 may then create a new file (typically for each pageof the source input file; however, in some embodiments, there may bemore than image, as discussed previously). In a next step 2506additional metadata 801 may be created and associated to files createdfrom the automatic content export processing. An example of metadata maybe a syntax text file which may comprise a definition of how individual“pages” are grouped or referred to each other to re-create/represent theoriginal source PDF file. Other metadata may also be added (for example,metadata associated to project details, project ID, or other descriptiveinformation describing, linking, sequencing, or other aspects of imagesand pages). For example, if an original PDF had, for example, ten pages,an associated metadata file may define which exported files may make-upthe original PDF pages and arrange them in a correct original sequence.In a next step 2507, content metadata processing may commence wherebycontent metadata manager 2405 may create and save any associatedmetadata files/data with the exported fixed-layout content files (e.g.images) to the fixed-layout exported content and metadata data store805.

In some embodiments, for “non-batch” files 2508, other programs (e.g.Adobe™ Photoshop™, CorelDraw™, etc.) may be used to provide a supervisedexport at step 2509 via semi-automatic or manual content exportprocessing of fixed-image layout content files to a desired quality.File loader 2409, on receipt of a request from user device 2401 a, mayupload exported files stored on a storage device (for example, to HDD52), for further processing by client metadata manager 2405, to, forexample, generate additional metadata at step 2507 (as described above).Accordingly, fixed-layout exported content and metadata 801 may befurther updated.

FIG. 26 is an exemplary process 2600 for the creation of elements areaitems associated with the fixed-layout exported content item. Theprocess starts at step 2602 by presenting, on a display screen of a userdevice, a fixed-layout content file so that element items may beassociated with the fixed-layout content item (for example, by receivingrequests from user device 2401 a. The element finder 2406 may display touser device 2401 a, based on a request from user device 2401 a, a fullcontent item (single file or dynamically re-assembled files). Theelement metadata manager 2407 may receive, from user device 2401 a, arange of configurations relating to how one or more new elements may beconfigured. In a next step, 2603, a plurality of parameters may bedefined to determine how the one or more element items may be presentedto a user interface of a display of, for example, user device 2401 a,and how interaction from user device 2401 a may behave with respect tothe one or more element items. Further, various states associated toelements describing behavior of the element item, may be determinedwithin an overall application system. Element area item configurationproperties, that may be stored as metadata, of the one or more elementsitems, may be: (a) the type of area that is being searched for (e.g. arectangle of any size); (b) defining one or more display color(s) of theelement area for various states; (c) if the element area allows dataentry (e.g. from a user device selecting within an element area of theone or more element areas), and type: select a format e.g. numeric,alphanumeric, or some other predefined data format; (d) the element areamay have additional properties such as: mandatory or non-mandatorydata-entry for an associated element area where data must be entered (ornot), by, for example, a user device of user devices 2401 a-n forvarious states; (e) a pre-configured display of other items within anelement area: such as a string of text, and other related parameters;(f) set display layer association; (g) associating a unique element areareference number; (h) linking element-areas logically such that if datais entered in a specific element-area, the next logical associatedelement-area is then allowed to accept data entry (or not); (i) anynumber of other behaviors determining function for a user interface oruser device display.

The type of element-area being searched (e.g. a rectangle), may be usedby the element finder 2406 to determine a number of and specificelement-area internal search directions (for example, from the searchpoint 1805) that element finder 2406 may use in the search area process.Examples of internal search directions for rectangles are illustrated inFIG. 18, 1803, 1804, 1805 1806 according to one embodiment of theinvention. Areas of different shapes may require a different number ofinternal search directions to ensure that boundaries of an element areais identified.

In a next step 2604, a select search start position process for findingthe element area item begins. The element finder 2406 may receive aninput, for example, from a user input device 49 or 50 (for example, auser pointing device, keyboard, touch screen device) associated to userdevices 2401 a that initiates a search process to start. An x-y 2Dcoordinate position of a location associated to the location receivedfrom user interaction, for example, via input device 50, may be providedto the element finder 2406, and must be inside an associated border ofthe element area that may need to be identified, and which may be partof the fixed-layout content item.

In a next step 2605, a find element x-y coordinates begins in order todetermine the element's x-y coordinates for each element definitionpoint (for example, as described in FIG. 7: 706, 707, 708, 709) on theselected element area (e.g. in a square or a rectangle element area,there are four primary definition positions, or corners, by which thearea can be re-created). Element finder 2406 may receive, from userdevice 2401 a, coordinates for an x-y start value from which to commencethe area search. The element finder 2406 may continue processingautomatically until it has identified all the x-y coordinate values forall the primary definition points. referring again to FIG. 18, in anembodiment, outline area 1801 may be contained in overall fixed-layoutarea 201, whereby a new element area to identify may be outline 1807,and whereby element finder 2406 may be prioritizing computations tofirstly identify the x-y position of element definition points 706, 707,708, 709.

In a next step, 2606, a calculation for element dimensions data maybegin by calculating dimensions data from x-y coordinate data calculatedin step 2605. The element creator 2408 may receive x-y coordinate valuesfrom element finder 2406 to calculate an additional set of data valuesthat may include element area width and height and an actual position ofthe element area with respect to the overall fixed-layout content item.Referring again to FIG. 4, the embodiment may comprise a calculation forwidth 401 and height 402. Referring again to FIG. 5, the embodiment maycomprise reference point 509 in the element area with respect tofixed-layout area reference point 501. Accordingly, reference points 501and 509 may then allow actual dimensions of an absolute x position 510,and y position 508 of the selected element area. With element area xposition 510 and y position 508, and fixed-layout content item xposition 514 (similarly, 301), and y position 515 (similarly, 302), andwidth 401, and height 402; accordingly, these dimensions may then beused to calculate derived values of fractions (or percentages whenmultiplied by 100). Accordingly, all x direction dimensions may bedivided by overall x dimension 301 (or 514) to result in a decimalfraction, similarly for x direction dimensions 302 (or 515) to arrive ata decimal fraction.

In a next step 2609, positional, dimensional, derived/fractional(including calculated values) data for items may be saved to element alldata store 805. Element creator 2408 may saves x-y coordinates,calculated and derived fraction data, and resultant data from theelement area properties step 2603. The element creator 2408 may saveassociated data to the element to data store 805. On completion of step2609, element finder 2406 may begin process 2600 at step 2604 foranother selection of a search start position to find another singleelement area request. In some embodiments, for a different element type,processing may begin again at step 2603.

In some embodiments, if element finder 2604 receives a request, from,for example, user device 2401 a, to find a range of adjacent cells (thatis, a plurality of adjacent areas of a fixed-layout content for whichelement areas are desired) in, for example, an external search direction1811 (referring to FIG. 18). Once complete, element finder 2406 maybegin again at step 2608 to automatically find a next element area.Accordingly, steps 2605, 2606 and 2609 and 2608 may be repeated until,for example, element finder 2406 may be unable find any additionaladjacent element areas. Referring again to FIG. 18, according to theembodiment, if a find element area 1812, for example, as selected byuser device 2401 a, with a goal to find element areas within find area1808, element finder 2406 may then iterate automatically to find thenext area 1809 and 1810 automatically, and from the outlined areas 1802,1803, 1804 contained in fixed-layout content item 201. Referring againto FIG. 18, search direction 1822 illustrates a different searchdirection, where a selection 1820 (for example, as selected by userdevice 2401 a) may initiate a search, by element finder 2406, toiteratively identify element area 1818, 1816, and 1814.

FIG. 27 is an exemplary process 2700 for a search for x-y coordinatesfor an element area item. In a first step 2701, element finder 2406 mayreceive coordinates, from a user device 2401 a, associated to an areainside an element area, element finder may store the x-y coordinatesvalues as start position coordinates xS-yS. In a next step 2702, elementfinder 2406 may then detect an associated pixel color at the xS-ySlocation and store, in database 806, the color data as a “start pixelcolor”. In a next step 2703, element finder 2406 may set an internalsearch direction associated to the element area type which has beenpreviously selected in step 2603. Examples of internal search directionare illustrated in FIG. 18, referring to 1803, 1804, 1805 1860 from astarting position of 1805 according to one embodiment of the invention.It should be noted that areas of different shapes may require adifferent number of directions to ensure that boundaries of the elementarea are identified.

Referring again to FIG. 18, examples of xS-yS are illustrated at 1805,1812, 1820. Referring again to FIG. 27, in a next step 2704, elementfinder 2406 may find coordinates for a next adjacent pixel and analyze apixel color at adjacent pixel location. Accordingly, if a first internalsearch direction is a +x direction 1804, then the next pixel coordinatescolor search may be at x-y coordinates equal to x(S+1)-yS coordinateposition. If the first internal search direction was in the −xdirection, for example direction 1805, then the next pixel color checkmay be at coordinates x(S−1)−yS. Further at step 2704, element finder2406 may calculate a next x(S+1)−yS coordinates for search direction1804, element finder 2406 may then reads a “current search pixel color”at this x(S+1)−yS coordinates location. In a next step 2705, elementfinder 2406 may compare the current search pixel color to the reference“start pixel color” and if these two values are the same, then iterationstep 2706 is complete. Accordingly, element finder 2406 may be reset tocontinue at step 2704 to execute a next find next pixel coordinate. Itshould be noted that element finder 2406 may continue process iteration2704, 2705, and 2704 until a “current search pixel color” is not thesame as the “start pixel color” thereby concluding the specific searchdirection (referring to set internal search direction at step 2703).Referring again to FIG. 18, a search direction and distance 1804 may beconcluded, thereby defining an x co-ordinate value for a position forelement definition positions 708 and 709. In some embodiments, ifelement finder 2406 sets the next search direction to be −x (referringto direction 1805), then an x coordinate value for element definitionpositions 706 and 707 may be next identified by element finder 2406. Andfollowing those two directions, element finder 2406 may set a nextdirection as +y (referring to direction 1806), then identifying a ycoordinate value for position 706, 708, and may then set, by elementfinder 2406, a final search direction which may be −y direction(referring to direction 1806), then the −y coordinate value, for elementdefinition positions 707 and 709, may be identified. In an iterationstep 2707, element finder 2406 may process at least a portion of alldefined search directions until all the internal search directions arefully completed. On completion of all required directions, by elementfinder 2406, x-y values for element definition positions 706, 707, 708,709 may be now identified for the element area, accordingly, elementfinder 2406 may calculate element area data points in process step 2606to calculate element dimensions data (referring to FIG. 26).

FIG. 28 is a block diagram illustrating an exemplary system architecture2800 for integrating fixed-layout components with external applicationsaccording to a preferred embodiment of the invention. According to theembodiment, programmatic user interface 2803 may be an application (forexample, workflow and interaction management systems such as SAP™,Siebel™, Oracle™, Genesys™, Cisco Call Manager™, other CRM systems,other custom build interaction, customer, and/or workflow managementsystems) that provides general application functionality and which maybe displayed on a display screen of a user device 2801 a-n. Programmaticuser interface 2803 may receive a request (for example, via anapplication programming interface, via a user interface, etc.) from auser device 2801 a-n to present and display an application to a userdevice display screen. Programmatic user interface module 2803 may beany application which has been developed using standard programmingtechniques where an application developer writes application code whichmay be then compiled/completed and presents the application logic anddisplay to an end user device. In some embodiments programmatic userinterface 2803 may be part of a server based system, for example an SaaSsystem, as is known in the art, and the like., whereby a graphicalpresentation to a user device 2801 a-n has been generatedprogrammatically.

Programmatic user interface 2803 may include the functionality to issuea request from anywhere within its application, to fixed-layout UI 2804.Fixed-layout UI 2804 may then issue a request to fixed-layout processor2805 to retrieve a fixed-layout component data from the fixed-layoutcomponent definition data. On receipt of the fixed-layout componentdata, by the fixed-layout processor 2805, which in turn may present datato fixed-layout UI 2804, and which may present on user-devices 2801 a-n.The fixed-layout UI 2804 may then present the component to an associateddevice display such that the fixed-layout component may be resizeddynamically to fit within the display area (referring to example FIG.10A: 1001).

Referring again to FIG. 1A, an overall display screen area 101 may havea programmatic area 103 and one fixed-layout display component area 102,as illustrated. Referring again to FIG. 1B, an overall display screenarea 105, programmatic application area 110, and fixed-layout displaycomponent areas 106, 107, 108, 109 is illustrated. In Referring again toFIG. 10A, programmatic area 103 may provide an area/window embedded intoa main programmatic application view with specified programmeddimensions of width 1005 and height 1003, and with position 1004 and1002 relative to the overall display area 101 boundary. Referring againto FIG. 10B, the fixed-layout content component definition configurationdata 806 may be loaded into the fixed-layout area/window outline area1001.

Fixed-layout UI 2804 may issue a request to fixed-layout processor 2805to retrieve the fixed-layout component definition data 806 from the datastore, and present this to fixed-layout UI 2804 which may then processesand display component definition data 806 on a display screen, of userdevice 2801 a-n, in area/window 1001. Fixed-layout UI 2804 may read andprocess all definition data 806 for a specific fixed-layout componentwhich may then enables the specific fixed-layout component to bereassembled from the component parts of; fixed-layout content item 201,element areas defined 202, 203, 204, 205, 206, 207, 208, calculatedfractional dimensions of each element 401, 402, their position 508, 510relative to the fixed-layout area, and user interactivity functionalitydefinitions 802, 803, 806 (that is, all part of 806).

Further, fixed-layout UI 2804 may issue a request to fixed-layoutprocessor 2805 to retrieve a specific set of fixed-content user data1313 depending on a requirement of the overall programmatic UI 2803.Fixed-layout component configuration data 806 may comprise uniquemetadata identifiers such that fixed-content user data 1313 may directlyassociated with each specific component in 806. In some embodiments,fixed-layout content component area, and all the element areas, may haveassociated and unique metadata identifiers/references. Referencesassociated to elements, components (for example, component IDs, elementIDs, and related other data defined in metadata) may then be used byfixed-layout processor 2805 to search for and retrieve specificfixed-content user data 1313 for element items contained within thefixed-layout component definition 806, and which may be part of aspecific component definition. Fixed-layout processor 2805 may transmitretrieved user data 1313 to the fixed-layout UI 2804 for presentation toa display area of, for example, user device 2801 a. The fixed layout UI2804 may receive any number of user interactions from user deice 2401 a.This fixed-layout UI 2804 may communicate with the fixed-layoutprocessor 2805 to determine a response to the user device, and to alsosave (or compute any additional data) any additional user (generated orcalculated) data to the fixed-content user data store 1313 which mayresult from these general interactions.

It should be noted that programmatic UI 2803 presentation on a userdevice 2801 a-n may vary significantly in terms of a form factor andorientation of the user device (referring to FIG. 11: 101, 1101, 1103,1105). Area/window 1001 for each of these examples may have differentdimensions and positional location within the associated device screen(referring to FIG. 11: 102, 1102, 1104, 1105, 1108). Fixed-layout UI2804 may then display component definition 806, and associated user data1313 inside these areas (referring to FIG. 11: 102, 1202, 1104, 1105,1108) such that a re-assembly and presentation to the user device may bepositionally and proportionally exact (as illustrated in FIG. 10B: 1001,FIG. 10C: 1009, FIG. 11: 1102, 1104, 1106, 1108).

Hardware Architecture

Generally, the techniques disclosed herein may be implemented onhardware or a combination of software and hardware. For example, theymay be implemented in an operating system kernel, in a separate userprocess, in a library package bound into network applications, on aspecially constructed machine, on an application-specific integratedcircuit (ASIC), or on a network interface card.

Software/hardware hybrid implementations of at least some of theembodiments disclosed herein may be implemented on a programmablenetwork-resident machine (which should be understood to includeintermittently connected network-aware machines) selectively activatedor reconfigured by a computer program stored in memory. Such networkdevices may have multiple network interfaces that may be configured ordesigned to utilize different types of network communication protocols.A general architecture for some of these machines may be describedherein in order to illustrate one or more exemplary means by which agiven unit of functionality may be implemented. According to specificembodiments, at least some of the features or functionalities of thevarious embodiments disclosed herein may be implemented on one or moregeneral-purpose computers associated with one or more networks, such asfor example an end-user computer system, a client computer, a networkserver or other server system, a mobile computing device (e.g., tabletcomputing device, mobile phone, smartphone, laptop, or other appropriatecomputing device), a consumer electronic device, a music player, or anyother suitable electronic device, router, switch, or other suitabledevice, or any combination thereof. In at least some embodiments, atleast some of the features or functionalities of the various embodimentsdisclosed herein may be implemented in one or more virtualized computingenvironments (e.g., network computing clouds, virtual machines hosted onone or more physical computing machines, or other appropriate virtualenvironments).

FIG. 17A illustrates an example of a conventional system bus computingarchitecture system 1700, and where the components are in electricalcommunication with each other using a bus 1707. The exemplary system1700 includes a processor unit 1708 and the system bus 1707 thatconnects the various items: memory 1701, RAM 1702, ROM 1703 to theprocessor 1708. The system processor 1708 may be supported by cache 1709performant memory, or be integrated as part of the processor 1708. Thesystem 1700 can copy data from the memory 1701 and/or the storage device1710 to the cache 1709 for rapid access by the processor 1708. Cache canprovide performance, rather than having the processor 1708 waiting fordata. These and other modules may control or be configured to controlthe processor 1708 to perform certain actions, and which may require theuse of memory 1701. The memory may consist of many different types andperformance characteristics. The processor 1708 may include ageneral-purpose component, or hardware or software modules, such asmodules 1711, 1712, stored in the storage device 1710, and configured tocontrol the processor 1708 as well as any special purpose processorwhere software instructions are incorporated into the actual processordesign. The processor 1708 may be a self-contained computing containingmultiple processors or cores, bus, memory controller, and cache etc. Theuser interaction 1704 with the device may be any number of mechanisms,such as keyboard, mouse, a touch-sensitive screen for gesture orgraphical input or other. The output-device 1705 can be display screen.The communications interface 1706 can typically govern and manage theuser input and system output. There is no restriction on operating onany particular hardware arrangement and therefore the basic featureshere may easily be substituted for improved hardware or firmware as theyare developed. The storage device 1710 is non-volatile memory can be ahard disk or other types of nontransitory computer readable media whichcan store data that is accessible by a computing device, such assolid-state memory device, flash memory, read only memory 1703 ROM.

FIG. 17B illustrates an example computer system 1715 which has a chipsetarchitecture that could be used to execute the described system andmethods and managing the graphical user interfaces on the devices. Thiscomputer system 1715 is an example of computer hardware, software andfirmware that can be used to implement the disclosed technology. Thesystem 1715 can include a processor 1717 representing any number ofphysically and/or logically distinct resources capable of executingsoftware, firmware and hardware configured to perform identified logiccomputations. The processor 1717 can communicate with a chipset 1716which in turn can control inputs to/from the processor 1717, outputs tothe output device 1721 and can read/write information to the storagedevice 1719 which can include any number of media types including forexample solid state media. Chipset 1717 can also read/write to the RAM1718 module. A chipset processor 1717 can output information to outputs1721 such as a device display, and can read/write information to astorage device 1719, which can include may media types, including solidstate media. Chipset 1717 can also read/write data to RAM 1718. Chipsetcan interface directly or indirectly with the output device 1721, andwhich could include a keyboard, a pointing device such as a mouse, or atouch-sensitive screen for gesture or graphical input. Inputs to thesystem 1715 can come from a variety of sources, human interface devicesand/or machine generated. Chipset 1717 can interface with one or morecommunications interfaces 1720 that can have different physicalinterfaces. Such communications interfaces can include interface forwired and wireless local or wide area networks. Some applications of themethods for generating, displaying, and using a GUI (graphical userinterface) disclosed herein can include receiving ordered informationdata over the physical interface or be generated by the processor 1717by analyzing data in the data storage 1719.

It can be appreciated that exemplary systems 1700, 1715 can have morethan one processor or be part of a group or cluster of computing devicesnetworked together to provide greater computing capability. For clarityof explanation in some instances the present technology may be presentedas including individual functional blocks comprising devices, devicecomponents, steps or routines in a method embodies in software, orcombinations of hardware and software.

Methods according to the above described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprisefor example, instructions and data which cause or otherwise configure ageneral-purpose computer, special purpose computer or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resource used can be available over acommunications network. The computer executable instructions may be, forexample binaries, other intermediate format instructions such asassembly language, firmware or source code. Examples ofcomputer-readable media that may be used to store instructions,information used, and/or information created during methods according todescribed examples include flash memory, USB devices comprisingnon-volatile memory, networked storage devices etc.

Devices implementing methods according to those disclosures can comprisehardware, firmware, and/or software can take a variety of form factors.Form factor examples can include laptops, smart phones, personal digitalassistants, small factor personal computers etc. Functionality describedherein can also be embodied in peripherals. Such functionality can alsobe implemented on a circuit board among different chips or differentprocesses executing in a single device etc.

A variety of examples and other information was used to explain aspectswithin the scope of the disclosed methods, no limitations should beimplied based on particular features or arrangements in such examples,as one of ordinary skill would be able to use these examples to derive awide variety for implementations.

Referring now to FIG. 20, there is shown a block diagram depicting anexemplary computing device 10 suitable for implementing at least aportion of the features or functionalities disclosed herein. Computingdevice 10 may be, for example, any one of the computing machines listedin the previous paragraph, or indeed any other electronic device capableof executing software- or hardware-based instructions according to oneor more programs stored in memory. Computing device 10 may be configuredto communicate with a plurality of other computing devices, such asclients or servers, over communications networks such as a wide areanetwork a metropolitan area network, a local area network, a wirelessnetwork, the Internet, or any other network, using known protocols forsuch communication, whether wireless or wired.

In one aspect, computing device 10 includes one or more centralprocessing units (CPU) 12, one or more interfaces 15, and one or morebusses 14 (such as a peripheral component interconnect (PCI) bus). Whenacting under the control of appropriate software or firmware, CPU 12 maybe responsible for implementing specific functions associated with thefunctions of a specifically configured computing device or machine. Forexample, in at least one aspect, a computing device 10 may be configuredor designed to function as a server system utilizing CPU 12, localmemory 11 and/or remote memory 16, and interface(s) 15. In at least oneaspect, CPU 12 may be caused to perform one or more of the differenttypes of functions and/or operations under the control of softwaremodules or components, which for example, may include an operatingsystem and any appropriate applications software, drivers, and the like.

CPU 12 may include one or more processors 13 such as, for example, aprocessor from one of the Intel, ARM, Qualcomm, and AMD families ofmicroprocessors. In some aspects, processors 13 may include speciallydesigned hardware such as application-specific integrated circuits(ASICs), electrically erasable programmable read-only memories(EEPROMs), field-programmable gate arrays (FPGAs), and so forth, forcontrolling operations of computing device 10. In a particular aspect, alocal memory 11 (such as non-volatile random-access memory (RAM) and/orread-only memory (ROM), including for example one or more levels ofcached memory) may also form part of CPU 12. However, there are manyways in which memory may be coupled to system 10. Memory 11 may be usedfor a variety of purposes such as, for example, caching and/or storingdata, programming instructions, and the like. It should be furtherappreciated that CPU 12 may be one of a variety of system-on-a-chip(SOC) type hardware that may include additional hardware such as memoryor graphics processing chips, such as a QUALCOMM SNAPDRAGON™ or SAMSUNGEXYNOS™ CPU as are becoming increasingly common in the art, such as foruse in mobile devices or integrated devices.

As used herein, the term “processor” is not limited merely to thoseintegrated circuits referred to in the art as a processor, a mobileprocessor, or a microprocessor, but broadly refers to a microcontroller,a microcomputer, a programmable logic controller, anapplication-specific integrated circuit, and any other programmablecircuit.

In one aspect, interfaces 15 are provided as network interface cards(NICs). Generally, NICs control the sending and receiving of datapackets over a computer network; other types of interfaces 15 may forexample support other peripherals used with computing device 10. Amongthe interfaces that may be provided are Ethernet interfaces, frame relayinterfaces, cable interfaces, DSL interfaces, token ring interfaces,graphics interfaces, and the like. In addition, various types ofinterfaces may be provided such as, for example, universal serial bus(USB), Serial, Ethernet, FIREWIRE™, THUNDERBOLT™, PCI, parallel, radiofrequency (RF), BLUETOOTH™, near-field communications (e.g., usingnear-field magnetics), 802.11 (WiFi), frame relay, TCP/IP, ISDN, fastEthernet interfaces, Gigabit Ethernet interfaces, Serial ATA (SATA) orexternal SATA (ESATA) interfaces, high-definition multimedia interface(HDMI), digital visual interface (DVI), analog or digital audiointerfaces, asynchronous transfer mode (ATM) interfaces, high-speedserial interface (HSSI) interfaces, Point of Sale (POS) interfaces,fiber data distributed interfaces (FDDIs), and the like. Generally, suchinterfaces 15 may include physical ports appropriate for communicationwith appropriate media. In some cases, they may also include anindependent processor (such as a dedicated audio or video processor, asis common in the art for high-fidelity AN hardware interfaces) and, insome instances, volatile and/or non-volatile memory (e.g., RAM).

Although the system shown in FIG. 20 illustrates one specificarchitecture for a computing device 10 for implementing one or more ofthe aspects described herein, it is by no means the only devicearchitecture on which at least a portion of the features and techniquesdescribed herein may be implemented. For example, architectures havingone or any number of processors 13 may be used, and such processors 13may be present in a single device or distributed among any number ofdevices. In one aspect, a single processor 13 may handle communicationsas well as routing computations, while in other aspects a separatededicated communications processor may be provided. In various aspects,different types of features or functionalities may be implemented in asystem according to the aspect that includes a client device (such as atablet device or smartphone running client software) and server systems(such as a server system described in more detail below).

Regardless of network device configuration, the system of an aspect mayemploy one or more memories or memory modules (such as, for example,remote memory block 16 and local memory 11) configured to store data,program instructions for the general-purpose network operations, orother information relating to the functionality of the aspects describedherein (or any combinations of the above). Program instructions maycontrol execution of or comprise an operating system and/or one or moreapplications, for example. Memory 16 or memories 11, 16 may also beconfigured to store data structures, configuration data, encryptiondata, historical system operations information, or any other specific orgeneric non-program information described herein.

Because such information and program instructions may be employed toimplement one or more systems or methods described herein, at least somenetwork device aspects may include nontransitory machine-readablestorage media, which, for example, may be configured or designed tostore program instructions, state information, and the like forperforming various operations described herein. Examples of suchnontransitory machine-readable storage media include, but are notlimited to, magnetic media such as hard disks, floppy disks, andmagnetic tape; optical media such as CD-ROM disks; magneto-optical mediasuch as optical disks, and hardware devices that are speciallyconfigured to store and perform program instructions, such as read-onlymemory devices (ROM), flash memory (as is common in mobile devices andintegrated systems), solid state drives (SSD) and “hybrid SSD” storagedrives that may combine physical components of solid state and hard diskdrives in a single hardware device (as are becoming increasingly commonin the art with regard to personal computers), memristor memory, randomaccess memory (RAM), and the like. It should be appreciated that suchstorage means may be integral and non-removable (such as RAM hardwaremodules that may be soldered onto a motherboard or otherwise integratedinto an electronic device), or they may be removable such as swappableflash memory modules (such as “thumb drives” or other removable mediadesigned for rapidly exchanging physical storage devices),“hot-swappable” hard disk drives or solid state drives, removableoptical storage discs, or other such removable media, and that suchintegral and removable storage media may be utilized interchangeably.Examples of program instructions include both object code, such as maybe produced by a compiler, machine code, such as may be produced by anassembler or a linker, byte code, such as may be generated by forexample a JAVA™ compiler and may be executed using a Java virtualmachine or equivalent, or files comprising higher level code that may beexecuted by the computer using an interpreter (for example, scriptswritten in Python, Perl, Ruby, Groovy, or any other scripting language).

In some embodiments, systems may be implemented on a standalonecomputing system. Referring now to FIG. 21, there is shown a blockdiagram depicting a typical exemplary architecture of one or moreaspects or components thereof on a standalone computing system.Computing device 20 includes processors 21 that may run software thatcarry out one or more functions or applications of aspects, such as forexample a client application 24. Processors 21 may carry out computinginstructions under control of an operating system 22 such as, forexample, a version of MICROSOFT WINDOWS™ operating system, APPLE macOS™or iOS™ operating systems, some variety of the Linux operating system,ANDROID™ operating system, or the like. In many cases, one or moreshared services 23 may be operable in system 20, and may be useful forproviding common services to client applications 24. Services 23 may forexample be WINDOWS™ services, user-space common services in a Linuxenvironment, or any other type of common service architecture used withoperating system 21. Input devices 28 may be of any type suitable forreceiving user input, including for example a keyboard, touchscreen,microphone (for example, for voice input), mouse, touchpad, trackball,or any combination thereof. Output devices 27 may be of any typesuitable for providing output to one or more users, whether remote orlocal to system 20, and may include for example one or more screens forvisual output, speakers, printers, or any combination thereof. Memory 25may be random-access memory having any structure and architecture knownin the art, for use by processors 21, for example to run software.Storage devices 26 may be any magnetic, optical, mechanical, memristor,or electrical storage device for storage of data in digital form (suchas those described above, referring to FIG. 20). Examples of storagedevices 26 include flash memory, magnetic hard drive, CD-ROM, and/or thelike.

In some embodiments, systems may be implemented on a distributedcomputing network, such as one having any number of clients and/orservers. Referring now to FIG. 22, there is shown a block diagramdepicting an exemplary architecture 30 for implementing at least aportion of a system according to one aspect on a distributed computingnetwork. According to the aspect, any number of clients 33 may beprovided. Each client 33 may run software for implementing client-sideportions of a system; clients may comprise a system 20 such as thatillustrated in FIG. 21. In addition, any number of servers 32 may beprovided for handling requests received from one or more clients 33.Clients 33 and servers 32 may communicate with one another via one ormore electronic networks 31, which may be in various aspects any of theInternet, a wide area network, a mobile telephony network (such as CDMAor GSM cellular networks), a wireless network (such as WiFi, WiMAX, LTE,and so forth), or a local area network (or indeed any network topologyknown in the art; the aspect does not prefer any one network topologyover any other). Networks 31 may be implemented using any known networkprotocols, including for example wired and/or wireless protocols.

In addition, in some embodiments, servers 32 may call external services37 when needed to obtain additional information, or to refer toadditional data concerning a particular call. Communications withexternal services 37 may take place, for example, via one or morenetworks 31. In various aspects, external services 37 may compriseweb-enabled services or functionality related to or installed on thehardware device itself. For example, in one aspect where clientapplications 24 are implemented on a smartphone or other electronicdevice, client applications 24 may obtain information stored in a serversystem 32 in the cloud or on an external service 37 deployed on one ormore of a particular enterprise's or user's premises.

In some embodiments, clients 33 or servers 32 (or both) may make use ofone or more specialized services or appliances that may be deployedlocally or remotely across one or more networks 31. For example, one ormore databases 34 may be used or referred to by one or more aspects. Itshould be understood by one having ordinary skill in the art thatdatabases 34 may be arranged in a wide variety of architectures andusing a wide variety of data access and manipulation means. For example,in various aspects one or more databases 34 may comprise a relationaldatabase system using a structured query language (SQL), while othersmay comprise an alternative data storage technology such as thosereferred to in the art as “NoSQL” (for example, HADOOP CASSANDRA™,GOOGLE BIGTABLE™, and so forth). In some embodiments, variant databasearchitectures such as column-oriented databases, in-memory databases,clustered databases, distributed databases, or even flat file datarepositories may be used according to the aspect. It will be appreciatedby one having ordinary skill in the art that any combination of known orfuture database technologies may be used as appropriate, unless aspecific database technology or a specific arrangement of components isspecified for a particular aspect described herein. Moreover, it shouldbe appreciated that the term “database” as used herein may refer to aphysical database machine, a cluster of machines acting as a singledatabase system, or a logical database within an overall databasemanagement system. Unless a specific meaning is specified for a givenuse of the term “database”, it should be construed to mean any of thesesenses of the word, all of which are understood as a plain meaning ofthe term “database” by those having ordinary skill in the art.

Similarly, some aspects may make use of one or more security systems 36and configuration systems 35. Security and configuration management arecommon information technology (IT) and web functions, and some amount ofeach are generally associated with any IT or web systems. It should beunderstood by one having ordinary skill in the art that anyconfiguration or security subsystems known in the art now or in thefuture may be used in conjunction with aspects without limitation,unless a specific security 36 or configuration system 35 or approach isspecifically required by the description of any specific aspect.

FIG. 23 shows an exemplary overview of a computer system 40 as may beused in any of the various locations throughout the system. It isexemplary of any computer that may execute code to process data. Variousmodifications and changes may be made to computer system 40 withoutdeparting from the broader scope of the system and method disclosedherein. Central processor unit (CPU) 41 is connected to bus 42, to whichbus is also connected memory 43, nonvolatile memory 44, display 47,input/output (I/O) unit 48, and network interface card (NIC) 53. I/Ounit 48 may, typically, be connected to keyboard 49, pointing device 50,hard disk 52, and real-time clock 51. NIC 53 connects to network 54,which may be the Internet or a local network, which local network may ormay not have connections to the Internet. Also shown as part of system40 is power supply unit 45 connected, in this example, to a mainalternating current (AC) supply 46. Not shown are batteries that couldbe present, and many other devices and modifications that are well knownbut are not applicable to the specific novel functions of the currentsystem and method disclosed herein. It should be appreciated that someor all components illustrated may be combined, such as in variousintegrated applications, for example Qualcomm or Samsungsystem-on-a-chip (SOC) devices, or whenever it may be appropriate tocombine multiple capabilities or functions into a single hardware device(for instance, in mobile devices such as smartphones, video gameconsoles, in-vehicle computer systems such as navigation or multimediasystems in automobiles, or other integrated hardware devices).

In various aspects, functionality for implementing systems or methods ofvarious aspects may be distributed among any number of client and/orserver components. For example, various software modules may beimplemented for performing various functions in connection with thesystem of any particular aspect, and such modules may be variouslyimplemented to run on server and/or client components.

The skilled person will be aware of a range of possible modifications ofthe various embodiments described above. Accordingly, the presentinvention is defined by the claims and their equivalents.

What is claimed is:
 1. A method for intelligent layering of interactiveprogrammatic elements for fixed content, comprising: an intelligentlayering computer comprising at least a processor, a memory, and aplurality of programming instructions stored in the memory and operatingon the processor, the programming instructions, when executed by theprocessor, cause the processor to configure and associate one or moreelement areas to fixed content comprising the steps of: receiving, at anexport manager, fixed context data from a data store; receiving, by anelement finder, a shape designation, from a user device; sending, by theelement finder, the fixed content data to a display device associated tothe user device; receiving, at the element finder, a selection from theuser device, the selection identifying an x-axis coordinate and a y-axiscoordinate, the coordinates associated to a position within the fixedcontent; establishing a search start position, the search start positionbased on the coordinates; determining, by the element finder, a searchpattern, the search pattern comprising a plurality of search directionsbased on the shape designation; finding, by the element finder,boundaries of an element area, using the search pattern, the boundariesdetermined by a change in pixel color by: (a) setting a current searchdirection based on a first search direction of the plurality of searchdirections; (b) initializing a pixel position as the search startposition; (c) analyzing a pixel color at the pixel position; (d) movingto an adjacent pixel along the current search direction (e) setting thepixel position to the position of the adjacent pixel (f) if the color ofthe current pixel is the same as the pixel color, repeat at step (c);(g) recording a boundary of a plurality of boundaries, the boundarybased on a location associated to the current pixel; (h) setting thecurrent search direction to a next search direction of the plurality ofsearch directions; (i) repeating at step (b) until all searchdirections, of the plurality of search directions, have been completed;receiving, at an element metadata manager, a plurality of propertiesfrom the user device, the plurality of properties defining a pluralityof behaviors for the element area; packaging, at the export manager, afixed-layout package comprising the plurality of boundaries and theplurality of properties.